Repository navigation
spec: issue-3582 Trace local mode - #3583
Conversation
PR validation — ✅ 3 passing
AI Session Checks — 🟢 85% ·
|
| Avg score | Sessions | Failing policies | Attribution | Files | Lines | Total Duration |
|---|---|---|---|---|---|---|
| 🟢 85% | 1 | 100% AI / 0% Human | 1 | +146 / -109 | 48h34m16s |
🟢 85% — 100% AI — ⚠️ 1 policies failing
-
Oct 11, 2026 21:43 UTC · 48h34m16s · $305.48 · 1.9k in / 1.5M out · claude-code 2.1.296 (claude-opus-4-8)
Change Summary
-
- Revises the issue-3582 spec around local trace behavior and clarifies export semantics.
- Adds trace local-init and export-path implementation details, including unsigned manifest markers.
- Restricts GUAC credentials to service-account keys and covers that path with focused tests.
AI Session Overall Score
-
🟢 85% — Strongly verified work, with one corrected spec-to-implementation drift worth checking.
AI Session Analysis Breakdown
-
🟢 93% · verification
-
🟢 Repeated builds, tests, and smoke checks backed the claimed outcomes. · High Impact
🟢 90% · solution-quality
-
🟢 Core fixes targeted the real mechanism rather than bypassing checks. · High Impact
🟢 88% · scope-discipline
-
No notes.
🟢 86% · user-trust-signal
-
No notes.
🟢 82% · context-and-planning
-
🟢 Wide tasks were grounded by reading specs, reviews, and code first. · Medium Impact
🟡 68% · alignment
-
🟠 The revised spec briefly outpaced the implementation until the export manifest was updated to match. · Medium Severity
💡 When a spec change alters observable output, pair it with the implementation follow-up in the same pass or mark it blocking immediately.
-
File Attribution
████████████████████100% AI / 0% HumanStatus Attribution File Lines modified ai docs/specs/issue-3582-trace-evidence-export.md+146 / -109
Policies (4, 1 failing)
Status Policy Material Messages ✅ Passed ai-config-ai-agents-allowedai-coding-session-d139ac- ✅ Passed ai-config-no-dangerous-commandsai-coding-session-d139ac- ⚠️ Failedai-config-no-secretsai-coding-session-d139ac- Secret (generic-password) detected in session content [turn=1458, source=tool_result, line=6]: 115: Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=1464, source=tool_result, line=115]: 115 Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=15, source=tool_result, line=115]: 115 Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=43, source=tool_result, line=100]: 100 Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=49, source=tool_result, line=140]: 140 Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=51, source=tool_result, line=132]: 132 Credentials: &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password],
- Secret (generic-password) detected in session content [turn=53, source=tool_result, line=117]: 117 response.Credentials = &sdk.Credentials{Password: [CHAINLOOP_TRACE_REDACTED:generic-password]
✅ Passed ai-config-mcp-servers-allowedai-coding-session-d139ac- -
Security Checks — ✅ 5 passing
✅ secret-scan
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | secrets-detection |
- |
✅ sast-scan
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | owasp-top10-2025 |
- |
| ✅ Passed | sast |
- |
| ✅ Passed | cwe-top25 |
- |
| ✅ Passed | cwe-top26-40-cusp |
- |
Scans not applied (3)
| Scan | Reason |
|---|---|
vulnerability-scan |
no manifest/lockfile changed |
github-actions-scan |
no workflow files changed |
iac-scan |
no IaC files changed |
Security context
✅ Nothing this change touches has a recorded security-fix history.
View in Chainloop ↗ · How this works ↗
Powered by Chainloop and Chainloop Trace
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
View guided diff | Re-trigger cubic
|
Do you think we should encrypt the sessions at rest on disk? |
migmartri
left a comment
There was a problem hiding this comment.
How does the UX look like? What flags? Does it require init? Can you init without server? Init today requires authentication
migmartri
left a comment
There was a problem hiding this comment.
please review the UX from the POV of seting it up offline
Design spec for a mode that runs the trace push-time assembly and writes the AI coding session evidence set to a local directory, with no control plane and no attestation. Refs #3582 Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
c468abc to
0901286
Compare
Revise the design so trace init --local is the primary enabling surface, which records a reserved local organization and a repository project so the setup contacts no control plane. trace run --export then wraps the agent and writes the evidence set to disk when the session ends, with no push. Refs #3582 Chainloop-Trace-Sessions: d139ac66-b95f-4920-ac38-12997996037d Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
Record the decisions the implementation settled. Local mode is marked per-clone in the trace state rather than in the shared repository config. The pre-push hook sends no attestation in local mode. A standalone trace export command writes the evidence of the sessions the hooks already recorded. Refs #3582 Chainloop-Trace-Sessions: d139ac66-b95f-4920-ac38-12997996037d Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
Scope R-001 and R-005 to the export phase, so a run that wraps the agent does not fall foul of the no-network requirement. Require the index to declare the export is unsigned and not an attestation. Replace the ambiguous "the mode" in the prose with "the export". Refs #3582 Chainloop-Trace-Sessions: d139ac66-b95f-4920-ac38-12997996037d Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
View guided diff | Re-trigger cubic
R-008, the summary, and the proposal read as though the push wrote the evidence to disk. State that the hook only skips attestation and writes nothing, and that the separate trace export command writes the evidence on demand. Refs #3582 Chainloop-Trace-Sessions: d139ac66-b95f-4920-ac38-12997996037d Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
Refocus the spec on recording AI coding sessions without a control plane, per review. A repository stores sessions on disk, configured in .chainloop.yml with traceStorage (CONTROL_PLANE default or LOCAL), an optional tracePath, and traceRequired (replacing requireTrace). The pre-push hook stores the session locally through the same assembly a push runs. Exporting an already-recorded session on demand is deferred to a future spec. Refs #3582 Chainloop-Trace-Sessions: d139ac66-b95f-4920-ac38-12997996037d Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
Summary
Chainloop Trace assembles a session's evidence on a
git pushand uploads a signed attestation to the control plane. This spec adds a mode that runs the same assembly and writes the result to a local directory, with no control plane and no attestation. Developers and tests then get the exact evidence a push would produce, on disk, for inspection and comparison. The export writes the evidence record and each material under its content digest, with a manifest.Open questions for reviewers: none.
We would like two reviewers to approve this spec before it merges.
Refs #3582
Drafted with the br:eng-spec skill (Claude Code).